Make project plan revisions idempotent - #8
Merged
Conversation
JulioMCruz
marked this pull request as ready for review
July 20, 2026 00:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The E2E change-request path produced duplicate proposal cards, duplicate task blocks, 429s, and late workflow messages in a newer chat thread.
Impact
A plan has one actionable proposal, PM retries do not duplicate structure, and task/workflow events remain attached to the workflow conversation.
Validation
npm test— 9 files, 44 tests passednpm run typechecknpm run buildProduction must set or remove its explicit
AGENT_RATE_LIMIT_MAXoverride to receive the new default.